x86/vmx: don't call __vmxoff() blindly
authorJan Beulich <jbeulich@suse.com>
Sat, 17 Sep 2011 15:26:37 +0000 (16:26 +0100)
committerJan Beulich <jbeulich@suse.com>
Sat, 17 Sep 2011 15:26:37 +0000 (16:26 +0100)
commit169da1b3c1fe01a9f3a7c58b19aca2c652a7231a
tree24e50996a7885423d5d8496ecb3acdcc8e112c76
parenta21a59fdfd162b3b47aa58c8d3e88a3de7b93221
x86/vmx: don't call __vmxoff() blindly

If vmx_vcpu_up() failed, __vmxon() would generally not have got
(successfully) executed, and in that case __vmxoff() will #UD.

Additionally, any panic() during early resume (namely the tboot
related one) would cause vmx_cpu_down() to get executed without
vmx_cpu_up() having run before.

Signed-off-by: Jan Beulich <jbeulich@suse.com>
xen/arch/x86/hvm/vmx/vmcs.c